chore(deps): update all non-major dependencies #67

renovate · 2025-08-11T02:59:01Z

This PR contains the following updates:

Package	Change	Age	Confidence
@eslint/config-inspector	`^1.1.0` -> `^1.3.0`
@eslint/js (source)	`^9.32.0` -> `^9.37.0`
@types/node (source)	`^24.2.0` -> `^24.7.0`
automd	`^0.4.0` -> `^0.4.2`
eslint (source)	`^9.32.0` -> `^9.37.0`
globals	`^16.3.0` -> `^16.4.0`
jiti	`^2.5.1` -> `^2.6.1`
pnpm (source)	`10.14.0` -> `10.18.1`
typescript (source)	`^5.9.2` -> `^5.9.3`
typescript-eslint (source)	`^8.39.0` -> `^8.46.0`
unbuild	`^3.6.0` -> `^3.6.1`

Release Notes

eslint/config-inspector (@eslint/config-inspector)

`v1.3.0`

Compare Source

Features

update deps (#146) (655b4a4)

`v1.2.0`

Compare Source

Features

display rule deprecated info (#141) (1c86b27)
upgrade to nuxt4, update deps (#142) (1947870)

eslint/eslint (@eslint/js)

`v9.37.0`

Compare Source

`v9.36.0`

Compare Source

Features

47afcf6 feat: correct preserve-caught-error edge cases (#20109) (Francesco Trotta)

Bug Fixes

75b74d8 fix: add missing rule option types (#20127) (ntnyq)
1c0d850 fix: update eslint-all.js to use Object.freeze for rules object (#20116) (루밀LuMir)
7d61b7f fix: add missing scope types to Scope.type (#20110) (Pixel998)
7a670c3 fix: correct rule option typings in rules.d.ts (#20084) (Pixel998)

Documentation

b73ab12 docs: update examples to use defineConfig (#20131) (sethamus)
31d9392 docs: fix typos (#20118) (Pixel998)
c7f861b docs: Update README (GitHub Actions Bot)
6b0c08b docs: Update README (GitHub Actions Bot)
91f97c5 docs: Update README (GitHub Actions Bot)

Chores

12411e8 chore: upgrade @eslint/js@9.36.0 (#20139) (Milos Djermanovic)
488cba6 chore: package.json update for @eslint/js release (Jenkins)
bac82a2 ci: simplify renovate configuration (#19907) (唯然)
c00bb37 ci: bump actions/labeler from 5 to 6 (#20090) (dependabot[bot])
fee751d refactor: use defaultOptions in rules (#20121) (Pixel998)
1ace67d chore: update example to use defineConfig (#20111) (루밀LuMir)
4821963 test: add missing loc information to error objects in rule tests (#20112) (루밀LuMir)
b42c42e chore: disallow use of deprecated type property in core rule tests (#20094) (Milos Djermanovic)
7bb498d test: remove deprecated type property from core rule tests (#20093) (Pixel998)
e10cf2a ci: bump actions/setup-node from 4 to 5 (#20089) (dependabot[bot])
5cb0ce4 refactor: use meta.defaultOptions in preserve-caught-error (#20080) (Pixel998)
f9f7cb5 chore: package.json update for eslint-config-eslint release (Jenkins)
81764b2 chore: update eslint peer dependency in eslint-config-eslint (#20079) (Milos Djermanovic)

unjs/automd (automd)

`v0.4.2`

Compare Source

compare changes

`v0.4.1`

Compare Source

compare changes

🩹 Fixes

pm-install: Use pnpm add instead of pnpm install (#122)
pm, pm-install: Add npm: prefix for deno (#115)
jsimport: Bun doesn't support url imports (#112)
Create missing output dir (#106)

📖 Documentation

Update config section (#107)

🏡 Chore

Update deps (a63bb3e)

❤️ Contributors

Daniel Rentz (@danielrentz)
Yvbopeng (@yvbopeng)
Huseeiin (@huseeiin)
Keito (@mst-mkt)
Selemon Brahanu (@selemondev)
Pooya Parsa (@pi0)

eslint/eslint (eslint)

`v9.37.0`

Compare Source

`v9.36.0`

Compare Source

`v9.35.0`

Compare Source

`v9.34.0`

Compare Source

`v9.33.0`

Compare Source

sindresorhus/globals (globals)

`v16.4.0`

Compare Source

Update globals (#309) 8b8a2d6

unjs/jiti (jiti)

`v2.6.1`

Compare Source

compare changes

🩹 Fixes

interop: Only passthrough default if it is not a promise (#408)

📦 Build

Revert to terser-webpack-plugin (#407)

🏡 Chore

Update bench (037c646)
Update deps (974ca40)
Remove unused code (8b41497)

❤️ Contributors

Pooya Parsa (@pi0)
Kricsleo (@kricsleo)

`v2.6.0`

Compare Source

compare changes

🔥 Performance

Lazy load babel transform (#405)

🩹 Fixes

cjs-interop: Handle function default exports (#396)
Always use native for node: specifiers (#392)

📦 Build

Migrate to rspack (#404)

🏡 Chore

Update deps (5123334)

✅ Tests

Update deno and bun native test ignores (df844f8)
New bench script (6404427)

❤️ Contributors

Pooya Parsa (@pi0)
Volodymyr Kolesnykov (@sjinks)
Jungwoo LEE <jungwoo3490@naver.com>

pnpm/pnpm (pnpm)

`v10.18.1`

Compare Source

Patch Changes

Don't print a warning, when --lockfile-only is used #8320.
pnpm setup creates a command shim to the pnpm executable. This is needed to be able to run pnpm self-update on Windows #5700.
When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

`v10.18.0`

Compare Source

Minor Changes

Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

Related PR: #10025.

Patch Changes

Retry filesystem operations on EAGAIN errors #9959.
Outdated command respects minimumReleaseAge configuration #10030.
Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
Don't fail with a meaningless error when scriptShell is set to false #8748.
pnpm dlx should not fail when minimumReleaseAge is set #10037.

`v10.17.1`

Compare Source

Patch Changes

When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #9974.
Fix state.json creation path when executing pnpm patch in a workspace project #9733.
When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #9987.

`v10.17.0`

Compare Source

Minor Changes

The minimumReleaseAgeExclude setting now supports patterns. For instance:
```
minimumReleaseAge: 1440
minimumReleaseAgeExclude:
  - "@&#8203;eslint/*"
```
Related PR: #9984.

Patch Changes

Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #9978.
When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #9979.

`v10.16.1`

Compare Source

Patch Changes

The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #9963.
Forcibly disable ANSI color codes when generating patch diff #9914.

`v10.16.0`

Compare Source

Minor Changes

There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:
```
minimumReleaseAgeExclude:
  - webpack
```
Related issue: #9921.
Added support for finders #9946.

In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:
```
pnpm why minimist
```
prints the chain of dependencies to any installed instance of minimist:
```
verdaccio 5.20.1
├─┬ handlebars 4.7.7
│ └── minimist 1.2.8
└─┬ mv 2.1.1
  └─┬ mkdirp 0.5.6
    └── minimist 1.2.8
```
What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:
```
module.exports = {
  finders: {
    react17: (ctx) => {
      return ctx.readManifest().peerDependencies?.react === "^17.0.0";
    },
  },
};
```
Now we can use this finder function by running:
```
pnpm why --find-by=react17
```
pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.
```
@&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
└── graphql-tag 2.12.6
```
It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:
```
module.exports = {
  finders: {
    react17: (ctx) => {
      const manifest = ctx.readManifest();
      if (manifest.peerDependencies?.react === "^17.0.0") {
        return `license: ${manifest.license}`;
      }
      return false;
    },
  },
};
```
Every matched package will also print out the license from its package.json:
```
@&#8203;apollo/client 4.0.4
├── @&#8203;graphql-typed-document-node/core 3.2.0
│   license: MIT
└── graphql-tag 2.12.6
    license: MIT
```

Patch Changes

Fix deprecation warning printed when executing pnpm with Node.js 24 #9529.
Throw an error if nodeVersion is not set to an exact semver version #9934.
pnpm publish should be able to publish a .tar.gz file #9927.
Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #9626.

`v10.15.1`

Compare Source

Patch Changes

Fix .pnp.cjs crash when importing subpath #9904.
When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #9913.

`v10.15.0`

Compare Source

Minor Changes

Added the cleanupUnusedCatalogs configuration. When set to true, pnpm will remove unused catalog entries during installation #9793.
Automatically load pnpmfiles from config dependencies that are named @*/pnpm-plugin-* #9780.
pnpm config get now prints an INI string for an object value #9797.
pnpm config get now accepts property paths (e.g. pnpm config get catalog.react, pnpm config get .catalog.react, pnpm config get 'packageExtensions["@babel/parser"].peerDependencies["@babel/types"]'), and pnpm config set now accepts dot-leading or subscripted keys (e.g. pnpm config set .ignoreScripts true).
pnpm config get --json now prints a JSON serialization of config value, and pnpm config set --json now parses the input value as JSON.

Patch Changes

Semi-breaking. When automatically installing missing peer dependencies, prefer versions that are already present in the direct dependencies of the root workspace package #9835.
When executing the pnpm create command, must verify whether the node version is supported even if a cache already exists #9775.
When making requests for the non-abbreviated packument, add */* to the Accept header to avoid getting a 406 error on AWS CodeArtifact #9862.
The standalone exe version of pnpm works with glibc 2.26 again #9734.
Fix a regression in which pnpm dlx pkg --help doesn't pass --help to pkg #9823.